fix: clarify difference between instance and definition references - #1716
Conversation
3e77912 to
4b484d7
Compare
This changes instance references to be required, while definition references are optional. It also changes the instance reference from process simulation to pipeline by removing the TARGET key.
4b484d7 to
5d91eae
Compare
jsolaas
changed the title
|
Does this lead to change in YAML? Before/after example? |
|
So, this will make it possible to use "any reference" whenever a reference is needed, so that when we parse and validate - we will always need to check that the type is correct and supported? E.g. to not reference to a process unit when a pipeline is expected etc? Or was this already the case, but never checked? |
tj098895
left a comment
tj098895
left a comment
There was a problem hiding this comment.
nice, I love when stuff I had thought of fixing just gets fixed :)
Always the case, not sure about the check though. We should be able to check that. |
2 participants
This changes instance references to be required, while definition
references are optional. It also changes the instance reference from
process simulation to pipeline by removing the TARGET key.